ASM has two Application Programming Interfaces (or APIs), which enable you to develop programs that automate many common ASM transactions. This section of the documentation deals with the Classic API. For more information on the RESTful Alemba API, see here.
API transactions can be categorized into:
- Availability Transactions
- Call Transactions
- CMDB Transactions, including Contract Transactions, Cost Center Transactions, Jurisdiction Transactions, Location Transactions, Organization Transactions, Person Transactions and Subscriber Group Transactions
- Knowledge Transactions
- System Transactions, including Session Transactions, Add Note Transactions, Attribute Transactions, Development Transactions, Message Transactions, Object Transactions and Stakeholder Transactions
- Workflow Transactions, including Task Transactions, and Workflow (Request) Transactions